User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.3) Gecko/2008101800 Gentoo Firefox/3.0.3 Build Identifier: 2.0.0.17 (20081018) When attempting to copy or move messages from another account or a local folder to a Gmail mailbox in TBird using IMAP, I receive this message: "Unable to append message to folder (Failure)". This seems to occur only with messages that either have an empty subject line or a subject of "Re:" (in other words, replies to empty subjects). I am not certain that this occurred on the first copy of such a message. However, now that I have encountered the error, I can reproduce it every time I try to copy any of a number of messages that fit the description (even if I copy one at a time). I believe this is a Thunderbird problem because I have successfully copied the same messages to my Gmail account using Evolution with IMAP. Reproducible: Always Steps to Reproduce: 1. Have a Gmail account using IMAP active in Thunderbird. 2. Choose a message or messages with empty subject lines in a local folder or other account. 3. Attempt to copy or move the messages, either by drag n dropping, or by using the context menu. Actual Results: Error message: "Unable to append message to folder (Failure)" Expected Results: Copied or moved the message successfully.

This works for me in Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1pre) Gecko/20090521 Shredder/3.0b3pre

Ian Young, can you attach IMAP log to this bug? ( See Bug 480529 Comment #1 & Bug 480529 Comment #16 for getting log ) Log lines from "append" command to the error("NO Unable to append ..." or "BAD Unable to append ...") is sufficient for first problem analysis. If account name/mail addr etc. is sensitive data for you, replace them by a string before open log to public, please.

I've attached a log of a failure and, in case it helps, a log of a very similar message that copied from the same source directory to the same destination as the failed message without complaint. On repeated copies, the failed message always fails and the successful message always succeeds. It also appears that my previous observation about empty subject lines was not entirely accurate, as these messages have Thunderbird's "(no subject)" text as the subject.

Ian, this sounds like a question for the gmail folks. If you copy the problem message to a new folder, and edit message as new, and remove the urls, does copying it work?

David, I realize this may turn out to be a problem on Gmail's end, but since Tbird has trouble when Evolution doesn't, this seemed like the right place to start the investigation. Removing the URLs seems to have no effect. Copying the message to another folder doesn't have any effect. However, I found that if I hand-edit the Local Folders file (my test case is copying from a local file to Gmail) and change only the Message-ID field for the failing message, it will copy successfully. Hope this helps.

Interesting. Changing the message-id how? And does this happen if you copy to a different gmail imap folder?

I edit ~/.thunderbird/xxxxx.default/Mail/Local Folders/junk.sbd/Inbox, making a change such as: @@ -47,7 +47,7 @@ Subject: (no subject) Thread-Topic: (no subject) Thread-Index: AcisHh14SPb6skOeRiyAteF8Kp0EEQ== -Message-ID: <481AB528.9050105@grinnell.edu> +Message-ID: <381AB528.9050105@grinnell.edu> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: Notice I am just arbitrarily altering a digit in the ID. After that the message will copy. And it yes, it still happens when I change the destination folder in Gmail.

very strange, what happens if you take the "bad" message id and overwrite the message-id in a good message, and try to upload that?

Well, this is weird. Overwriting the message id alone does not produce the error, but if I overwrite both the Message-ID and the Date fields with the values from the "bad" message, then I can produce the error on a formerly good message.

I'm wondering if gmail has decided these are spam messages

Gmail keeps "single copy of mail" only. 1. Append a mail (say added as uid=A) 2. Append the mail again => OK (added as uid=(A+1) if ordinal IMAP) 3. Fetch mails => uid=(A+1) doesn't exist. It looks for Tb that uid=(A+1) was deleted&expunged by other client between 2 & 3. I believe "duplicated mail detection" is based on at least Message-id:, Subject:, From:, To:, Date:, and mail body. (If Subject: was changed before step 2, it was considered "new mail" by Gmail IMAP even though same Message-Id:.) Biggest difference between Tb and Evolution looks for me difference between "Subject: (no subject)" and "Subject:".

Another Gmail's particularity is "conversation based mail management" which is similar to "mail threading" of mail client. At Gmail's Web Interface, unit of display is "conversation", not "mail", although "unit of presentation to Gmail IMAP client" is mail(=UID). I guess Gmail's bug around it.

I couldn't reproduce phenomenon with mail of "Subject: (no subject)", with Gmail IMAP, by "copy local mail twice to Gmail IMAP folder". Ian Young, did you copy the mail by Evolution first? Does original mail of "Subject:" only already exist in "All Mail"? ("[Gmail]/All Mail" folder via IMAP)?

Tb trunk passed "Subject:" and "Subject: " to Gmail IMAP (i.e. as-is, "(no subject)" is not added by Tb), and Gmail kept single new instance of mail for them. All local mail data other than Subject header is absolutely same. So, for Gmail, "Subject:" == "Subject: " and "Subject:" != "Subject: (no subject)". IP address used for imap.gmail.com was 209.85.201.109 or 209.85.201.111 in my test. > I edit ~/.thunderbird/xxxxx.default/Mail/Local Folders/junk.sbd/Inbox, (snip) As David says, I'm suspecting "Spam detection by Gmail" now.

WADA, I didn't copy from Evolution first. The bug originally showed up before I had even installed Evolution (I started looking for workarounds when Tbird wouldn't work). I'm not sure what you're asking about All Mail - I have been copying to an IMAP folder corresponding to one of my Gmail labels, but it doesn't seem to make a difference whether there are labels applied or not, either to the existing copy in Gmail, or to where I am copying. While I agree that messing with the local files by hand seems likely to trigger Gmail's spam catchers, remember that when I originally encountered the bug, it was copying regular messages from a real account that hadn't been altered and shouldn't have set off any spam flags. I'm sorry this is all so vague, I'll play around a bit more and try to figure out a reliable way to reproduce this.

(In reply to comment #17) > I'm not sure what you're asking about All Mail Special Gmail's FOLDER of "All Mail", "Spam", "Trash" can be considered "real mail folder", and "single instance of mail" is held in one of them. I asked "(1) is true or not" first. (1) The mail is already held in "All Mail" ([Gmail]/All Mail) (2) The mail is already held in "Spam" ([Gmail]/Spam) (3) The mail is already held in "Trash" ([Gmail]/Trash) (4) The mail doen't exist in any of above folders.

Ok, I understand. As of the time of report, a copy of the message existed in "All Mail". I tried moving it to trash and saw no change. I tried deleting it forever from Gmail and found myself able to copy the previously failed message. After that I could copy the failed message repeatedly without error. I still haven't figured out how to reproduce this with a new message.

(In reply to comment #19) > As of the time of report, a copy of the message existed in "All Mail". Do you remember When/How the mail was initially held by Gmail? (1) Original mail is mail arrived at Gmail in the past (2) Original mail was extracted from other POP3 account(s) by Gmail (3) You uploaded the mail via Gmail IMAP using Tb (4) You uploaded the mail via Gmail IMAP using Evolution or other mailer

All the mail that has caused conflicts should have arrived at Gmail by being uploaded with Tb (3).

(In reply to comment #19) > Ok, I understand. As of the time of report, a copy of the message existed in > "All Mail". I tried moving it to trash and saw no change. I tried deleting it > forever from Gmail and found myself able to copy the previously failed message. > After that I could copy the failed message repeatedly without error. > I still haven't figured out how to reproduce this with a new message. Probably MalDB entry for the mail was generated by old Gmail and was corrupted by bug of old version of Gmail in the past. Once corrupted, newly uploaded mail of "Subject: " is considered as duplicated mail, and the old/corrupted entry is used forever. As you deleted the old/corrupted Mail DB entry, I think there is no way to reproduce proble with current Gmail. Closing as INVALID(Gmail's old bug), because I think there is no need to keep this bug open. Please re-open, if you can reproduce problem.